This PR bundles several related improvements to the editor and simulation:

Display node now renders simulation output

• CCComponentEditorRendererNodeDisplayRenderer reads the value of the Pixels input pin in play mode and paints each cell black/white accordingly, instead of always rendering an empty grid.

Time-stepped input values

• InputValueKey is now [CCComponentPinId, TimeStep] instead of just CCComponentPinId, so manually-set input values are tracked per time step.
• getInputValue falls back to the previous time step's value when none is set for the current step, keeping inputs sticky as time advances.
• Callers (ComponentPin renderer, simulation harness) are updated to pass the current timeStep.

Pin bit-width policy refactor

• Introduced IntrinsicComponentPinBitWidthPolicy with three variants: inferred, fixed (with calculateBitWidth), and configurable (with isSplittable).
• Replaced the large switch in getComponentPinBitWidthStatus with a policy lookup via the new IntrinsicComponentDefinition.getPinAttributesByPinId / getByComponentId static accessors.
• Each intrinsic in intrinsics/definitions.ts now declares an explicit bitWidthPolicy (e.g. display.Pixels derives its width from resolution.x * resolution.y).
• defaultBitWidth is threaded through ComponentEvaluationContext and simulateComponent, so unfixed pins can fall back to the parent's resolved width instead of hard-coded 1.

Reconnect connections on bit-width change

• In NodePinPropertyEditor, after a manual bit-width change, connections are re-evaluated: still-compatible ones are recreated instead of being silently dropped.

Reset button and default sample extraction

• The default sample circuit setup was extracted from store/react/index.tsx into a new store/samples/default.ts (setupDefaultSample).
• The home page's disabled "New File" button is removed in favor of a "Reset" button (with confirmation) that re-seeds the store with the default sample.
• resetStore accepts an optional JSON payload; when omitted, the default sample is restored.

Auto-cleanup of orphaned nodes

• CCNodeStore.mount now listens for components.willUnregister and unregisters nodes whose componentId or parentComponentId matches the removed component, preventing dangling references.